Add IPv6 support for IPBlocksInfo CRD#1422
Merged
Merged
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1422 +/- ##
==========================================
- Coverage 77.02% 76.94% -0.09%
==========================================
Files 156 156
Lines 22048 22061 +13
==========================================
- Hits 16983 16974 -9
+ Misses 3859 3858 -1
- Partials 1206 1229 +23
🚀 New features to boost your workflow:
|
b90dc50 to
3409afc
Compare
dantingl
reviewed
May 11, 2026
Collaborator
dantingl
left a comment
There was a problem hiding this comment.
Can you also add test done in commit message?
00eb219 to
4dcde75
Compare
Contributor
|
I notice one more change will need for this PR nsx-operator/pkg/nsx/services/ipblocksinfo/ipblocksinfo.go Lines 261 to 270 in 6ae0434 Here we add Subnet cidr with privatetgw/public access mode to ipblocksinfo.
|
Support VpcConnectivityProfile.Ipv6Blocks in IPBlocksInfo sync Include paths from VpcConnectivityProfile.Ipv6Blocks into the same externalIPBlockPaths set as ExternalIpBlocks during IPBlocksInfo reconciliation. This ensures that external IPv6 IP blocks assigned to a VPC connectivity profile have their CIDRs and IP ranges surfaced in the IPBlocksInfo CR (ExternalIPCIDRs / ExternalIPRanges) without requiring any CRD schema change. Signed-off-by: Wenqi Qiu <wenqi.qiu@broadcom.com>
4dcde75 to
a590014
Compare
poojav25
reviewed
May 21, 2026
Contributor
|
LGTM |
poojav25
approved these changes
May 21, 2026
poojav25
added a commit
to poojav25/nsx-operator
that referenced
this pull request
May 21, 2026
Upstream landed two commits since the branch point (ff79596): - 214f2a5 Sync defaultIPv6PrefixLength from VPCNetworkConfiguration to Subnet(Set) (vmware-tanzu#1417) - 33a3e95 Add IPv6 support for IPBlocksInfo CRD (vmware-tanzu#1422) Both upstream commits bumped nsxt and nsxt-mp to v0.0.0-20260506074423. Our branch had already bumped nsxt to v0.12.1-0.20260517061842-508c01aec2fc (May 17, newer) to get IpAddressType/Ipv6AllocationPrefixLength model fields required for this PR. Resolution: - nsxt: keep our v0.12.1-0.20260517061842-508c01aec2fc (newer, required for IPv6) - nsxt-mp: take upstream's v0.0.0-20260506074423-13747423203f (we had old March version) Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Support VpcConnectivityProfile.Ipv6Blocks in IPBlocksInfo sync
Include paths from VpcConnectivityProfile.Ipv6Blocks into the same
externalIPBlockPaths set as ExternalIpBlocks during IPBlocksInfo
reconciliation. This ensures that external IPv6 IP blocks assigned
to a VPC connectivity profile have their CIDRs and IP ranges
surfaced in the IPBlocksInfo CR (ExternalIPCIDRs / ExternalIPRanges)
without requiring any CRD schema change.
TestDone:
1.Enable VpcIpv6 FSS, Restart proton service.Replace
manager, Restart the Operator2.Create an IPv6 IPBlock (at the global /infra level)
3.Create a VPC Connectivity Profile
Retrieve the default VPC Connectivity Profile details

5.Create VPCNetworkConfiguration